Overview

• Adding integration tests for Java and Dotnet. These are similar to the existing Node/Python integration in that they just test very basic functionality - we get logs/traces from the lambda function. These tests are meant to be our starting point and serve as example setup for other integration tests.
• Fixed how we are filtering logs to use @lambda.request_id:{requestId}. This makes it use log attributes instead of checking the actual log message.
• Updated stack cleanup step to just execute CLI command instead of CDK command. There was a slight issue when cleaning up the Java/Dotnet stacks due to their code assets, so the CLI command was easier.
• Added tag the tag extension_integration_test: true to all of the stacks to make it easier to cleanup stacks if it gets missed (deployed locally and forgot to clean up, pipeline cancelled before cleanup step, etc.) A follow up item is to create a lambda function to periodically run and clean up all old stacks with this tag.

Testing

• Integ tests for this PR passed.
• Checked AWS account and confirmed that there are no stacks with prefix integ-61910f24